The logic for converting ObjectQL filters to MongoDB queries has a critical flaw when handling mixed AND/OR logic. The current implementation creates a new group when the logic operator changes, but it doesn't properly handle complex cases like [['a', '=', 1], 'and', ['b', '=', 2], 'or', ['c', '=', 3]].

Expected behavior: This should produce { $or: [{ $and: [{ a: 1 }, { b: 2 }] }, { c: 3 }] }
Actual behavior: The current logic will create separate groups but won't properly nest AND within OR operations.

The issue is that when the logic changes from 'and' to 'or', the previous group is not properly closed and combined. This can lead to incorrect query results where filters are applied with the wrong boolean logic.

The code doesn't validate that the string operator is one of the expected values ('and' or 'or'). If an invalid string operator is passed (e.g., 'xor', 'not', or any typo), it will be silently accepted and treated as a logic operator without validation. This could lead to unexpected behavior where invalid operators create new logic groups that don't match the intended query semantics.

Add validation to ensure only 'and' and 'or' are accepted as logical operators, throwing an ObjectQLError for invalid operators.

The class declaration states it implements both Driver and DriverInterface, but the change removes DriverInterface from the implements clause. However, the class header comment at line 82 still claims it implements Driver. The actual code only implements Driver now, which is correct, but the comment should be updated to clarify that Driver interface already includes all methods from DriverInterface (as mentioned in the file header comment at lines 15-16).

The escapeRegex function accepts 'str: string' but immediately calls String(str) on it. This suggests the function expects to handle non-string inputs, but the type signature doesn't reflect this. Either change the parameter type to 'any' or 'unknown' to match the runtime behavior, or remove the String() conversion and enforce that callers pass strings. The current inconsistency between the type signature and implementation could hide bugs where non-string values are incorrectly passed to regex operations.

The regex operators (contains, like, startswith, endswith) handle value conversion by calling escapeRegex(value), but they don't validate that value is a string or can be safely converted to a string. If value is null, undefined, or a complex object, the String(value) conversion in escapeRegex might produce unexpected results. Consider adding validation to ensure value is a string or can be safely converted, or throw a clear error for invalid input types.

The supports object includes properties (queryFilters, queryAggregations, querySorting, queryPagination, queryWindowFunctions, querySubqueries) that are not defined in the DriverInterface specification from @objectstack/spec. The DriverInterface.supports interface only defines: transactions, joins, fullTextSearch, jsonFields, and arrayFields.

Adding non-standard properties could cause issues with code that expects the standard DriverInterface shape. Either these properties should be added to the @objectstack/spec DriverInterface, or they should be removed from this implementation to maintain strict compliance with the specification.

The find method creates a shallow copy of every record ({ ...value }) during the initial record collection phase, even for records that may be filtered out by the query. For large datasets, this could cause unnecessary memory allocation and GC pressure.

Consider deferring the copy operation until after Mingo filtering is applied, so only records that match the query are copied. This would improve performance when filters significantly reduce the result set.

The variable 'conditions' is declared but never used in the function. It should be removed to improve code clarity and avoid confusion.

The between operator validation only checks if the value is an array with length === 2, but doesn't validate that the array elements are actually comparable values (numbers, dates, etc.). If someone passes [null, null] or [undefined, undefined] or mixed types like [1, 'string'], the MongoDB query will be created but may produce unexpected results. Consider adding validation to ensure both bounds are defined and of compatible types.

Unused import DriverInterface.